SCR error when running "Update-StorageGroupCopy" command
I was able to Enable SCR, but when I go to seed the database using the "Update-StorageGroupCopy" I get the following message....Any ideas?"There is no StandbyReplicationNode String found for node "Our Target Server Name"
May 28th, 2009 5:05pm
Are you passing Target Machine name into -StandbyMachine switch?
Update-StorageGroupCopy -Identity <Server\StorageGroupName> -StandbyMachine <SCRTargetMachine>
How to Seed a Standby Continuous Replication Target
http://technet.microsoft.com/en-us/library/bb738131.aspxAmit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com
Free Windows Admin Tool Kit Click here and download it now
May 28th, 2009 5:32pm
Yes, Im using our SCRtargetmachine NAMEafter the -"StandbyMachine" Im also running it from the Update-StorageGroupCopy from the target machine
May 28th, 2009 5:37pm
Do I need to specify the "Source" server after the Identity switch?I ran the command like this:Update-StorageGroupCopy -Identity "First Storage Group" -StandbyMachine "Our target Server"Should I add the source server\storage group?
Free Windows Admin Tool Kit Click here and download it now
May 28th, 2009 5:43pm
It should pickup local server there but you can try by giving server name\storage group format...Amit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com
May 28th, 2009 5:56pm
You have received the error below during the Update-StorageGroupCopy, right?
There is no valid StandbyReplicationNode string found for node
Please make sure that all requirements in the SCR planning have been met
Please reproduce the issue and see if theres any error/warning event in the application log
Free Windows Admin Tool Kit Click here and download it now
May 29th, 2009 1:13pm
I was able to Enable SCR, but when I go to seed the database using the "Update-StorageGroupCopy" I get the following message....Any ideas?
"There is no StandbyReplicationNode String found for node "Our Target Server Name"
Hi All,
This issue will come if your domain controllers are not replicated each other after enabling the storage group copy to scr target. Force the replication between domain controllers and execute
Update-StorageGroupCopy -Identity <Server\StorageGroupName> -StandbyMachine <SCRTargetMachine>
Thanks,
Santhosh
Santhosh Sivaraman MCITP: Microsoft Exchange Server 2007/2010 | MCSE/MCSA
December 5th, 2010 1:11am